Inside the non recommended packages there is a recommended freebsd version  :) Install packages from same freebsd version pfsense uses. Current version is freebsd 8.1 p6. *-stable packages could depend on shared libs that are not present o outdated on pfsense.

Anyone can write a package and submit it if you've got the skills!  ;) See: http://doc.pfsense.org/index.php/Developing_Packages If not then consider raising a bounty to get it done. Steve

You have control of who does what on your installation. Kern.securelevel is more of a needed option on multi-user installation while pfSense is not like that.

You'll need to forward port 587/TCP if people are connecting remotely to send email through your server (as opposed to 25/TCP for other mail servers).  You'll need 110/TCP and 143/TCP for POP and IMAP and port 80/TCP (and hopefully 443/TCP) for Webmail. I'd highly recommend that you configure your SMTP server and POP/IMAP server to support TLS and your web server to support HTTPS. Those port forwards should cover your required remote access

An outbound nat could simulate a proxy, that's the only way I could do this. This way,server logging will have only firewall ip address. A proxy could set a X-forwarder-ip and a web server(for example) is able to log clients ip.

You could edit /etc/inc/system.inc and edit the function that makes syslog.conf and have it direct those logs to somewhere else (or /dev/null)

You probably want /usr/local/www/status_rrd_graph_img.php

Thank you Steve that worked perfectly!

Thanks jimp. I will change the hard disk and check again. Out of curiosity - how did you know that this is storage related? Atul.

@wallabybob: If its a private IP address then pfSense goes out to the web to get the public IP address. That was the piece of "magic" I was trying to validate, as my searches didn't find anything that spelled it out. Everything else, I already knew, as I've been running pfSense for quite a while now, with ZoneEdit handling the DNS for me. @wallabybob: If the public IP address changes more frequently than daily then it would be better if the IP address of the monitored interface changed more frequently OR if the address was polled more frequently. I think my searches revealed that I could load the cron package, and change the frequency of the check. The IP only changes very rarely, but on those odd occasions, waiting for a number of hours for the update could be quite frustrating. Now all I have to check, is if either the FTP "helper" in pfSense when it has a "private" WAN IP, or the VoIp box, is smart enough to modify the passive FTP replies to use the public IP.  I know that pfSense, when it has the public IP on the WAN interface copes quite happily. Cheers.

You can use the FreeRADIUS package for that, though generally people who are using RADIUS have central RADIUS servers.

Not unheard of with certain types of connectivity, though you generally shouldn't ever see that. It's usually indicative of some kind of network problem. Your description should eliminate the cause from anything on your network, it's something I'd bring up with the ISP.

Jimp thank you but I have used the prerequisites script prior to the update and it said all is fine. However I will try to reproduce this by using a VM, let's see if it is going to happen again.

OK, thanks very much. I'll try bridging the router first then and see if pfSense recoonects OK after link loss. I must say that I very much appreciate the rapid and helpful replies - what a great community this is  :)

Thanks to all for the input. It was a big help.